home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19941031-19941221
/
000399_news@columbia.edu_Mon Dec 12 14:08:33 1994.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA09623
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Mon, 12 Dec 1994 09:08:41 -0500
Received: by apakabar.cc.columbia.edu id AA12966
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Mon, 12 Dec 1994 09:08:39 -0500
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: term type in telnet-macro (Kermit 3.14)
Date: 12 Dec 1994 14:08:33 GMT
Organization: Columbia University
Lines: 49
Message-Id: <3chlh1$cl0@apakabar.cc.columbia.edu>
References: <3bul2u$47d@infosrv.rz.unibw-muenchen.de>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3bul2u$47d@infosrv.rz.unibw-muenchen.de>,
Peter Schmolck <p41bsmk@kommsrv.rz.unibw-muenchen.de> wrote:
>I'm using MS-Kermit 3.14 Beta-14. My UNIX-hosts do not know what to do
>with "vt320", and when trying to adjust my mscustom.ini definitions I
>noted an inconsistency (or bug?). ... the myhost define in mscustom.ini:
>
> define myhost -
> telnet myhost 23 vt320,-
> if success assign myhost telnet \v(session)
>
>set the terminal type, and not only the TELNET-negotiated "telnet
>term-type" (which I rather preferred the macro to do).
>
Well, as the accompanying comment says, it's only a sample, which you should
adjust for the host(s) you are actually using, e.g.:
set telnet term-type vt220,-
telnet myhost,-
if success assign myhost telnet \v(session)
Kermit sends its actual terminal type during TELNET negotiations UNLESS you
have given a SET TELNET TERM command, which overrides the actual terminal
type, but only for the purposes of telling the TELNET server what kind of
terminal type you have. This is useful, for example, if Kermit's terminal
type is VT320, but the host knows the same terminal by a different name, such
as VT300, and does not recognize Kermit's terminal name.
>When I changed the myhost define from vt320 to vt220 the result was, that --
>expectedly -- the status line entry changed to VT220, but --unexpectedly--
>the remote TELNET server still received a "VT320". (??)
>
I checked this just now and it didn't happen to me. Probably you just
continued the same session, and the terminal type was not renegotiated?
>BTW, mskermit.bwr says: "... to create an override string with command
> SET TCP/IP TELNET-TERM-TYPE."
>Instead this should read either "set tcp/ip term-type" or "set telnet
>term-type".
>
You're right, we'll fix it. Thanks!
- Frank
x
x
x
x
x
x
x